Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loki #1826

Merged
merged 2 commits into from
Oct 30, 2024
Merged

Loki #1826

merged 2 commits into from
Oct 30, 2024

Conversation

Page-
Copy link
Contributor

@Page- Page- commented Oct 30, 2024

No description provided.

@Page- Page- requested a review from a team October 30, 2024 12:46
@Page- Page- enabled auto-merge October 30, 2024 12:46
This avoids an issue where we clear the logs buffer before the loki
write path has a chance to consume/transform it

Change-type: patch
thgreasi
thgreasi previously approved these changes Oct 30, 2024
Copy link
Member

@thgreasi thgreasi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since getLokiBackend is already memoized with an once, I don't expect this to have any measurable impact but lgtm.

nvm, I just read the commit message...

@@ -132,6 +132,8 @@ function handleStoreErrors(req: Request, res: Response, err: Error) {
res.status(500).end();
}

const lokiBackend = LOKI_ENABLED ? await getLokiBackend() : undefined;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hope the top level await would not cause any unexpected issues 😬

@Page- Page- merged commit 0a47be6 into master Oct 30, 2024
51 checks passed
@Page- Page- deleted the loki branch October 30, 2024 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants